Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update unified notebook with a dropsondes plot #17

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

JuleRadtke
Copy link
Collaborator

I updated the unified notebook with a reference to a paper from Heike and plotting additionally measurements from the dropsondes (rh). This is a try to include them into the same plot with the radar, but I don't know if that might make the plot too busy?

@tmieslinger
Copy link
Collaborator

Hi @JuleRadtke, that's a good idea.
However, could you merge your branch with the current master branch? I am no 100% sure, but that might have caused the checks to fail ;-)

@JuleRadtke
Copy link
Collaborator Author

Ja I try

ds_bahamas_selection.altitude.plot(ax=ax1, x='time', color = 'black', label = 'flight altitude')
ax1.legend(loc ='upper left')
ds_radar_selection.dBZ.plot(ax= ax1, x='time', cmap ='cubehelix' )
ds_radar_selection.dBZ.plot(ax= ax1, x='time', cmap ='cubehelix')
im= ds_dropsondes_selection.rh_mat.plot(ax=ax1,x='time', cmap = 'bone_r', add_colorbar=False )
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remember that we said we would like to have the dropsondes in the radar plot. Now that I look at it, it seems to suggest that at certain times the a dropsonde passes through a cloud (in the radar data), while this is not necessarily or most likely not true. Do you think we confuse people with that?
Alernatively, I could imagine having a seperate third panel in the plot showing lat, lon and the flight path from BAHAMAS (the circle) and dropsonde paths colored by the RH just like you did, but displaying their path in lat lon instead of time. What do you think about that?
(Or even showing it in 3D with lat, lon, height, but that might be too much ;-))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants